I believe we need to remove the whole resources section here.

nit: need to fix the indentation (of comments) within the podTemplate section.

Done

We should list the deprecated fields, at least at a high level. Like:

- Removed the following deprecated fields in favor of `podTemplate`:
    - `crdbCluster.resources.*`
    - `crdbCluster.podLabels.*`
    - `crdbCluster.topologySpreadConstraints.*`

etc.

That'll also make it easier for me to identify which parts of the docs need to be updated to remove reference to deprecated, so if for some reason we don't want to list this out in the release note I could still use that.

I understand to know before hand which fields are deprecated. However this change would make the CHANGELOG.md very log. Should we add that description here or I can add that in the ticket so it would be easier for you to write the documentation. This will add additional 10-12 line specific to deprecation in CHANGELOG.

cc @pritesh-lahoti

Personally I think 10-12 lines is acceptable. I've put similar lists in breaking changes/release notes in the past and AFAIK it was received well - people appreciate having the detail when you introduce a breaking change like deprecation/removal, and if they need to ctrl+F a field it's useful having it in the list. Best if we can have sub-bullets for each field like I proposed in my first comment, rather than individual release notes for every deprecation.